im thinking its probably worth it to split this contract up into multiple. it would be a lot easier to maintain each individual monitoring function if they need to be tweaked or upgraded (less gas costs to do individual deployments).
another thing to consider is using a proxy for each monitoring function contract, allowing them to updated individually. this would have the benefit of not needing to change anything in hypernative if we need to do an update.
open to thoughts here as i'm not sure yet what the best path is.

im thinking its probably worth it...

maybe for simplicity's sake, we just make this a proxy and use a single contract for now. if we get to a point of wanting to make change or add functionality, we can reassess if a single contract is the best route, but for now, a single upgradeable proxy is probably easiest.

the only concern there is who is the admin? i think there is a msig we can use to approve upgrades.

Invariant Monitor contract

Generated at commit: e1d216497f58f9e53a34aac208150a280f4de60d

🚨 Report Summary

For more details view the full report in OpenZeppelin Code Inspector

@pmckelvy1 This is ready, included the morpho change, deployed and upgraded the monitors in Base and Mainnet